Read any computer science textbook for background on stacks. They are a basic data structure that play a very important role in building software.
At UserLand Software, we needed a Frontier-based stack for development we're doing on top of a communications software package. When connected to the host there's a limit of 30 minutes per session. However, the traversal the script does can take longer than 30 minutes. Solution, every time the script dives into a topic, it pushes its address on a stack. Every time thru the loop a sub-script checks to see if the timer expired. If so, it logs off, then logs back on. Then it uses the paths stored in the stack to restore the state, so the outer loop has no idea that the connection has been broken and re-established.
No doubt there are many other uses for Frontier stacks. That's why we have documented and released the stack suite, so other script writers can use stacks in their scripts. To see how stacks work, have a look at the stack.test script. Click on the Debug button and then click on Follow to see how it runs.
Note that this isn't a "normal" suite -- it doesn't insert a menu. In that way, it's like the "states" suite that's included with Frontier 1.0.
How to Install
-------------
1. With Frontier running, double-click on suites.stack to install the stack suite.
2. Open the table.uniqueName folder and double-click on the table.uniqueName file to install this new verb which the stack suite calls.
3. Launch DocServer, use the Load Text File command in the File menu to load the verb docs for the stack suite and table.uniqueName.
